Architecture of GCB for Service Mesh and HTTPS/2 Support with Metadata

The following diagram illustrates the architecture of Gigamon Containerized Broker for service mesh and HTTPS/2 support with metadata environment.

1. The GCB Controller is registered with GigaVUE-FM and the traffic policy is deployed on the GCBs.
2. Communication of configuration, data, and statistics to and from GCB is performed through the GCB Controller Service. GigaVUE-FM communicates with the GCB PODs through the GCB Controller.
3. Each GCB POD is registered with GigaVUE-FM and the traffic policy is deployed on the GCBs.
4. The Pcapper collects the network traffic and sends the HTTP packets to GCB service through mTLS authentication. Refer to Configure mTLS Authentication for detailed information.
5. In the GCB service, the received HTTP packets are load balanced across the available GCB PODs.
6. GCB PODs filters the packets based on the metadata.
7. The filtered HTTP packets from GCB PODs are tunneled directly to the Tools or through the V Series nodes on OpenStack environment. Refer to the GigaVUE Cloud Suite for OpenStack Configuration Guide for more information on V Series configuration on OpenStack environment.
8. GCB Controller collects the data from GCB PODs and sends the collected statistics and heartbeats to GigaVUE-FM through mTLS authentication. Refer to Configure mTLS Authentication for detailed information.